Fix severity_in_level SQL function #1312
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What:
This fixes the conditions for "high" severity in the
severity_in_level
SQL functionWhy:
The "high" case had a condition that should only apply for "medium", making it so "high" results are never shown.
How:
Check a report that should contain "high" severity results.
Without the patch they should be hidden even when the filter is set correctly. With the patch they should appear again.
Checklist: